-
Notifications
You must be signed in to change notification settings - Fork 34
K8s auto-instrumentation details and example (Node.js) #59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@trentm , thanks a lot for your review here. I will consider everything you have mentioned here, but in some of the topics we had already changed those sentences (sorry I hadn't told you before about it). I'll ping you and make comments as soon as I apply the changes. Thanks a lot! |
Co-authored-by: Mike Birnstiehl <[email protected]>
Co-authored-by: Trent Mick <[email protected]>
Co-authored-by: Trent Mick <[email protected]>
Co-authored-by: Trent Mick <[email protected]>
Co-authored-by: Trent Mick <[email protected]>
|
Thanks a lot @trentm for your help here! I think we are ready for merging / final review. FYI I have removed also the |
Co-authored-by: Trent Mick <[email protected]>
Adding document
docs/kubernetes/operator/instrumenting-nodejs.mdwith details for instrumenting Node.js applications on kubernetes with the EDOT Node.js and the operator.@trentm , if possible I'd like your review on this:
init container to copy the SDK to a shared volumeplus a configuration in the main container to use the SDK throughNODE_OPTIONSenv var, but I'm not sure.This PR is similar similar to:
#54 (Java)
#58 (Python)